Hi Jemma,
I had the same problem that you are currently facing. The poeple in this forum have been more than gratious with there help on this issue, but it is impossible to find the complete solution in any one place. Since this is the case, I am going to attempt to combine all of the contributed tips and give a complete solution. For convienience I am following the IBM faq and inserting corrections where needed, (the original is at
http://www.developer.ibm.com/tech/faq/individual/0,,2:79325,00.html). This worked for me on a server running Windows 2000 SP3, Domino 6.0.2 CF2, and version 5.0 of the Websphere plugin on the same machine.
Part I - Configuring Domino
1 - Add 'HTTPEnableConnectorHeaders=1' to your notes.ini
2 - In the server document, goto the Ports->Internet Ports->Web section, specify the TCPIP port number that you want the Domino HTTP stack to use. (I used 1080)
3 - Still in the server document goto the Internet Protocols->Domino Web Engine tab. Under the Generating References section, Specify yes to use IIS. Select your protocol, port, and hostname. ( I used http, 1080, and www.yourdomain.com ) Remeber these settings, you need them for the Websphere plugin setup.
Part II - Installing the Webshere plugin
1 - Create the following directory, I used the C: drive but any will work, C:\WebSphere\AppServer. Create the following directories under it: bin, config, etc, and log.
2 - Copy the WebSphere plugin files from your c:\domino\data directory:
2.1 - For both 4.0 or 5.0 copy from <path to your domino data dir>\domino\plugins\plugin-cfg.xml to C:\WebSphere\AppServer\config\
2.2 For 4.0 copy from <path to your domino data dir>\domino\plugins\was40\ both plugin_common.dll and iisWASPlugin_http.dll to C:\WebSphere\AppServer\bin\
or for 5.0 copy from <path to your domino data dir>\domino\plugins\was50\ iisWASPlugin_http.dll to C:\WebSphere\AppServer\bin\ ( the other dll is not required for 5.0 plugin)
3 - Add the WebSphere plugin config entry to the registry.
For 4.0 create a new key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server\4.0
For 5.0 create a new key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server\5.0.0.0
In either case, create a string value under the created key called 'Plugin Config' and assign it a value of the complete path to your plugin-cfg.xml file. ( In my case it was C:\WebSphere\AppServer\config\plugin-cfg.xml )
4 - Configure the WebSphere plugin configuration file, C:\WebSphere\AppServer\config\plugin-cfg.xml, to point to the Domino server from part I.
4.1 Assign the server group
<ServerGroup Name="domino_web_servers">
<Server Name="Domino Server">
<Transport Hostname="server.company.com" Port="1080" Protocol="http"/>
</Server>
</ServerGroup>
4.2 Define the URI group
<UriGroup Name="domino_host_URIs">
<Uri Name="/*.nsf*"/>
<Uri Name="*/domjava/*"/>
<Uri Name="*/icons/*"/>
</UriGroup>
4.3 Define the virtual host group.
<VirtualHostGroup Name="domino_host">
<VirtualHost Name="*:*"/>
</VirtualHostGroup>
4.4 Finally tie all these entries together as a route.
<Route ServerGroup="domino_web_servers" UriGroup="domino_host_URIs" VirtualHostGroup="domino_host"/>
Part III - Configuring IIS to Use the Plugin
1 - Open the Internet Services Manager from the Administrator Tools in the Control Panel.
2 - Right click on the website you are enabling the integration on and choose New->Virtual Directory, then click next.
3 - Name the directory sePlugins, no other name will work. Click next. B
4 - Browse to the folder containing your WebShere plugins, ( C:\WebSphere\AppServer\bin\ ), then click next.
5 - Allow only Run Script and Execute permissions for the new virtual directory, click next, then finish.
6 - Right click the machine name in the tree in the left pane and choose properties.
7 - On the 'Internet Information Services' tab, select 'WWW Service' in the drop down box and select Edit.
8 - Click the ISAPI Filters tab.
9 - Click Add.
10 - For filter name enter: iisWASPlugin
11 - For Executable, browse to the WebSphere bin directory and select "iisWASPlugin_http.dll"
12 - Close all windows by choosing OK.
13 - Restart your system.
Part IV
Test your system by entering your website address in the browser, if you get your http start page, great! Then append homepage.nsf to the end of your URL, if the Domino home page opens all is good.
Sorry for the long post. I hope this helps some.
Later,
Don
Return to top
. . RE: iisWASPlugin Revisited... IIS/i... (~Chloe Lopjipyo... 5.Sep.03) 
Print this page
